General message handling interface for ld that allows the user to
select the message type of the specified message numbers. The
_n_u_m_l_i_s_t is a comma (',') or dash ('-') separated list of message
numbers.
eeeerrrrrrrroooorrrr====_n_u_m_l_i_s_t
Treat each message on the _n_u_m_l_i_s_t as an error.
wwwwaaaarrrrnnnniiiinnnngggg====_n_u_m_l_i_s_t
Treat each message on the _n_u_m_l_i_s_t as a warning.
iiiinnnnffffoooo====_n_u_m_l_i_s_t
Treat each message on the _n_u_m_l_i_s_t as an info message.
vvvveeeerrrrbbbboooosssseeee====_n_u_m_l_i_s_t
Treat each message on the _n_u_m_l_i_s_t as a verbose message.
ooooffffffff====_n_u_m_l_i_s_t
Ignore each message on the _n_u_m_l_i_s_t.
For example, ----LLLLDDDD____MMMMSSSSGGGG::::wwwwaaaarrrrnnnniiiinnnngggg====33333333 tells the linker to treat message
33, which by default is an error, as a warning. Similarly,
----LLLLDDDD____MMMMSSSSGGGG::::wwwwaaaarrrrnnnniiiinnnngggg====33333333::::ooooffffffff====44447777----66668888 tells the linker to treat message 33 as
a warning and to ignore all messages from 47 to 68 inclusive.
Fatal errors can not be modified by ----LLLLDDDD____MMMMSSSSGGGG::::
----UUUU Undefined symbols are not considered an error when this is supplied.
As a result, one can create an executable with undefined symbols.
Referencing an undefined symbol during execution may cause a
segmentation fault and a core dump.
----wwwwooooffffffff _n_u_m_l_i_s_t
This allows a user to specify a comma-separated list of numbers of
warnings which the linker is to suppress. For example, ----wwwwooooffffffff
5555,,,,11117777,,,,22223333 turns off warnings numbered 5, 17 and 23. If you are
linking using the cccccccc(_1) command, this flag should be passed to the
An object's segments must not overlap and all of the object's addresses
must be less than 0x80000000. The stack starts at 0x80000000 and grows
down through lower addresses therefore space should be left for it. The
default text segment address is 0x10000000 with the data segment
immediately following the text segment. The default is that the bss
segment follows the data segment.
When creating an executable object runnable on Unix, a.out,
/_u_s_r/_l_i_b/_c_r_t_1._o Should be the first object loaded and /_u_s_r/_l_i_b/_c_r_t_n._o
should be last following any libraries. The compiler drivers (_c_c(1),
_f_7_7(1), and _p_c(1)) automatically load these object files in the proper
order. Note that if lllldddd is invoked directly, those two objects will not be
loaded automatically. It is the user's responsibility to specify them
explicitly.
A single registry file, either with ----cccchhhheeeecccckkkk____rrrreeeeggggiiiissssttttrrrryyyy or ----uuuuppppddddaaaatttteeee____rrrreeeeggggiiiissssttttrrrryyyy
is allowed. If multiple registry files are provided, all except the last
one are silently ignored.
Be careful when using ----ddddeeeellllaaaayyyy____llllooooaaaadddd or when linking against an object that
was built ----ddddeeeeffffaaaauuuulllltttt____ddddeeeellllaaaayyyy____llllooooaaaadddd as the symbol preemption rules are
different: symbols are resolved from the delay loaded object as if the
object were last on the link line.
Archives that are built with ----CCCC produce COFF style archive headers. The
linker will no longer recognize such archives.
PPPPaaaaggggeeee 11118888
LLLLDDDD((((1111)))) LLLLDDDD((((1111))))
The following group of options have been superseded by the ----eeeellllssssppppeeeecccc
